Same screen quick pay button

ABSTRACT

A payment button on a device, such as a mobile phone, allows the user to remain on the window or page from which an item was selected for purchase. When the user is ready to purchases, the button is selected, and the user simply enters an identifier, such as a password or PIN, and the transaction is processed. The button remains on the same screen and changes during different stages of the payment process.

BACKGROUND

1. Field of the Invention

The present invention generally relates to on-line payments.

2. Related Art

More and more consumers are purchasing items and services overelectronic networks, such as the Internet. Consumers routinely searchfor and purchase products and services from merchants and individualsalike. The transactions can take place directly between an on-linemerchant or retailer and the consumer, where payment is typically madeby entering credit card or other financial information. Transactions canalso take place with the aid of an on-line payment provider, such asPayPal, Inc. of San Jose, Calif. Such payment providers can maketransactions easier and safer for the parties. Purchasing through theInternet from the convenience of a consumer's home, office, or virtuallyanywhere (with mobile devices) is one main reason why on-line purchasesare growing faster and faster.

Typical payment flows with on-line purchases provide the consumer with apayment or checkout button or link that is selected when the consumer isready for payment. Once selected, such as by clicking, the consumer istaken to a new checkout or payment page. The consumer then enters anyrequested information and confirms payment. One disadvantage to thispayment flow is that the consumer is taken away from the merchant orproduct page, which may lessen the consumer experience and precludefurther shopping or browsing on the page. Another disadvantage is thatthe consumer may be required to enter information, such as credit cardnumber, billing address, etc., which may be cumbersome andtime-consuming.

These problems may be even more prevalent in small mobile devices, suchas phones, having small screen sizes and keyboards or keypads. Withmobile devices, the consumer may want to remain on the merchant orproduct/application page because Internet navigation is more difficult.Furthermore, the small keyboards/keypads make it more inconvenient toenter information onto a payment page.

Thus, there is a need for a more effective way of making on-linepayments without the disadvantages discussed above.

SUMMARY

In accordance with an embodiment of the invention, a consumer, who hasmade a payment through a payment provider, such as PayPal, is able toselect a payment button to make a payment for one or more selecteditems, products, applications, or digital goods. The payment button ison the merchant or application page. Once selected, either by clickingor tapping, the payment button changes to request the consumer to entera password, PIN, or other identifier for the consumer account. Onceentered, the consumer taps or selects the button again, and the buttonanimates to show the payment being processed. Once completed, the buttonshows the payment sent. If the purchased good is an application or otherdigital good, downloading can automatically begin after confirmation ofpayment. Throughout the payment process, the payment button remains onthe merchant or application page, and the consumer is not taken to a newpayment page.

This type of payment button and flow can be specific to a device, whereonce the consumer makes an initial payment, the payment button will beavailable to the consumer in any subsequent payment transactions withthe device. The payment button and flow may also be available in generalon any device, as long as the consumer has set up the account with thepayment provider, and the consumer enters information that properlyidentifies the consumer, consumer account, and maybe the device.

By keeping the payment button and flow on the same merchant orapplication page (instead of opening up a new window), the consumer isable to continue to look at both the item information and paymentprocessing, and navigate to other pages if desired. Also, by allowingthe consumer to enter a simple, easy-to-remember identifier, such as aPIN, password, phone number, or email, the consumer can quickly andeasily make an on-line payment.

These and other features and advantages of the present invention will bemore readily apparent from the detailed description of the embodimentsset forth below taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart showing a process for making an on-line paymentaccording to one embodiment;

FIG. 2 is a flowchart showing a process performed by a payment providerfor processing an on-line payment according to one embodiment;

FIG. 3 shows various stages of a payment button through a paymentprocess according to one embodiment;

FIG. 4 is a block diagram of a networked system used in an on-linepayment flow with an embodiment of the invention; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more embodiments of the present disclosure.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

FIG. 1 is a flowchart 100 showing a process for making an on-linepayment according to one embodiment of the present disclosure. At step102, the consumer locates an item or items for purchase. This can bedone through any device with an Internet browser, such as a mobilephone, PDA, PC, etc. Thus, an item can be located by browsing theInternet, finding an appropriate merchant or retailer site, andselecting the item for purchase. Locating an item can also includeselecting an application or digital good from an on-line store. Suchitems are simply downloaded onto a consumer or recipient device, asopposed to a physical good that is received at a physical location.Examples of digital goods include an image, such as to send to someoneelse on a networking site or for personal use, such as for an avatar.Applications may include applications available through a store such asiTunes for the iPhone by Apple.

Once the item(s) are located, the consumer proceeds to checkout orpayment at step 104. In one embodiment, the merchant page orapplications details page includes a payment button that the user canselect when ready for checkout or payment. Selection can be made bytapping or clicking on the button. The payment button may include thename of the payment provider, such as PayPal, Inc. of San Jose, Calif.If the consumer does not have an account with the payment provider, asdetermined at step 106, the consumer is taken to a page where theconsumer can sign up for an account at step 108. This may includeopening a new window for the payment provider site, which may requestspecific information about the consumer. In one embodiment, theinformation includes some combination of the consumer's name, billingaddress, mailing address, credit card information, bank accountinformation, user name, and password or PIN. The payment provider mayalso request whether the consumer wants to set limits on the account,either in general or for “quick payments,” which is a way for consumersto quickly pay for an item. Limits may include daily dollar limits,transaction limits (both in number and/or in dollars), and monthlydollar limits.

In one embodiment, after the consumer as signed up for the paymentaccount or if the consumer has an established account, a determinationis made at step 110 as to whether the consumer has made a payment orquick payment through the payment provider account. If the consumer hasnot made a payment through the payment provider, which can be on thespecific device, on any device, or using a specific payment option ofthe payment provider (i.e., some sort of “quick pay” in differentembodiment, the consumer must first go through a payment flow at step112. For example, the payment flow may include having the consumer enteran email, phone number, password, and/or PIN, either in the same windowor in a new window. After the requested information is entered, thepayment request is processed at step 118.

If the consumer has made a suitable payment through the paymentprovider, as determined at step 110, a payment button appears on thesame screen as the merchant or application page. The button may appearafter a successful purchase through the merchant or application. Thisbutton may be different than a payment button for the payment providerwhen the consumer has not gone through a suitable payment flow. With thepayment button on the same page, the consumer selects this button atstep 114 to initiate payment. The button may be selected by tapping orclicking on it. Note that in other embodiments, the determination atstep 110 is skipped, such that after a consumer has an account with thepayment provider, the consumer proceeds directly to step 114.

Once the button is selected, the button changes to request the consumerto enter a password, PIN, or other identifier. This may be simplyindicated with something like “Enter Password.” In one embodiment, thecustomer then enters the requested information, such as by typing on akeyboard or virtual keypad, at step 116. In another embodiment, theconsumer first taps or clicks on the button before entering theinformation. For example, tapping or clicking on the button may replacethe message (e.g., “Enter Password”) with a blank field and cursorindicator at the beginning of the field. After entering the requestedinformation, the consumer transmits the information, such as by hittinga return button on the keyboard or tapping or clicking on the buttonagain. Communication of the information may be by any means, such asthrough the Internet, Bluetooth, or a wired connection, using suitablecomponents such as antennas and processors. The button changes again,indicating that the payment request is being processed, at step 118. Thebutton may animate to show the request is processing or simply flash amessage like “Processing . . . ”

Processing may be conventional for the payment provider. For example,the password or requested information is transmitted to the paymentprovider. The payment provider searches its database for a matchingpassword or information. The payment provider may also compareinformation about the device the request was transmitted from (such as aphone number from a mobile device) to information corresponding to anauthorized account. The payment provider also processes purchaseinformation, such as the price of the item(s). After processing, thepayment provider determines whether the payment request is approved atstep 120. A decline of the request can be for various reasons, includingincorrect password or identifier or purchase request exceeds a pre-setlimit, such as a dollar limit or a transaction number limit. If therequest is declined, the consumer and/or merchant can be notified atstep 122. Notification may be on the button, a separate window, textmessage, or any suitable mode. The notification may also include thereason for the decline, and may allow the consumer to re-enter thepassword.

If, as determined at step 120, the payment request is approved, thebutton on the customer device changes to notify the customer at step124. The notification may be a simple message on the button, such as“Payment Sent” or “Approved.” If the purchased item is a downloadableitem, such as an application, the download may begin, at step 126,automatically as soon as the payment is approved or sent. After thedownload is completed, the consumer will have the item on the device. Ifthe purchased item is a physical good, the merchant can deliver the itemby a suitable method, such as shipping or arranging a physical pick-up.After the payment has been approved, the payment button may remain onthe screen or disappear. The consumer can then continue shopping ornavigate to other pages for possible further purchases using the samescreen payment button.

FIG. 2 is a flowchart 200 showing steps performed by a payment providerto process an on-line payment, according to one embodiment. At step 202,the payment provider installs the payment button on a consumer's device,such as a mobile phone. Installation of the payment button may be by anysuitable means, such as through the Internet, Bluetooth, Near FieldCommunications (NFC), WiFi, or a wired connection, using suitablecomponents such as antennas and processors of the user device andpayment provider. The button or “same screen quick pay button,” asdescribed herein, remains on the same screen as the merchant site orapplication page. Note that certain conditions may have to be met beforethe same screen quick pay button is made available to the consumer. Forexample, in addition to having an account with the payment provider, theconsumer may also be required to have made a payment on the devicethrough the payment provider, signed up for the feature (e.g., settinglimits on payments made through the button), and/or made an on-linepayment through the payment provider on any device.

Once installed and available to the consumer, the payment provider waitsfor a payment request from the consumer using the payment button. Thepayment request is received, at step 204, when the consumer selects thepayment button. Upon receipt of the request, the payment provider sendsto the device a request for a password or other identifier at step 206.The payment provider then receives a password from the consumer at step208. Once all the necessary information is received, the paymentprovider processes the request at step 210. Necessary information mayinclude the consumer's password or ID, the consumer device ID (e.g.,phone number), purchase information (e.g., amount, item(s),description), and/or merchant information. This information may becommunicated or transmitted to the payment provider at once orseparately, such as at step 204 when the payment request is firstreceived and/or at step 208 when the password is received.

Using the information, the payment provider determines, at step 212,whether to approve the payment request. The approval determination canbe based on any suitable criteria of the payment provider, includingvalid account, not exceeding pre-set spending/transaction limits, and/orvalid user. If the payment request is denied, the payment provider sendsa notification at step 214. The notification can be sent to the consumerand/or the merchant and may include reasons for the denial.

If the payment request is approved, the payment provider transfers therequested funds, at step 216, from the consumer's account to themerchant or recipient. If the merchant or recipient also has an accountwith the payment provider, the funds are simply transferred betweenaccounts. If the merchant does not have an account with the paymentprovider, the payment provider may transfer the funds to a designatedaccount, such as a bank account with a routing and account number, orthe payment provider may request the merchant to sign up for an accountwith the payment provider to receive the funds. Once the funds aretransferred, the payment provider sends a notification, at step 218, tothe consumer and/or the merchant. At that time, the payment portion ofthe transaction is completed by the payment provider.

Note that the payment button may appear during various times when theuser is using a device. For example, if the user is playing a game onthe device and wishes to purchase a next level of the game or anupgrade, the payment button may appear so that the user can stay on thegame page and quickly and easily purchase the next level or upgrade. Thegame may be then be upgraded with a download from the game developer orother entity.

FIG. 3 shows a screen 302 of a mobile device, along with various stagesof a payment button during a payment process, according to oneembodiment. In this example, the mobile device is a phone. Screen 302includes a merchant or application details page 304 and a payment button306. When the consumer is ready to pay and selects payment button 306,the button changes to request entry of a password, shown as button 308.The consumer then selects the button and enters the requested passwordor information onto the button, as shown in button 310. The button thenanimates, such as a moving checkerboard, shown as button 312, to showthe request being processed. In one embodiment, if a certain time haspassed, such as three seconds, text appears on the button. This is shownas button 314, with the text indicating to the consumer that thetransaction is still processing. The text can be “Logging in . . . ,” asshown, or other text, such as “Processing . . . ” After processing,assuming the payment request was approved, the button again changes toindicate the payment was sent, shown as button 316. Note that throughoutthe different changes in the payment button, the button remains on samescreen or window as the merchant or application page, i.e., the usercontinues to be able to view the merchant or application page whilemaking the on-line payment.

FIG. 4 is a block diagram of a networked system 400 used in an on-linepayment flow according to an embodiment of the invention. System 400includes a client device 410, a merchant server 440, and a paymentservice provider server 470 in communication over a network 460. Paymentservice provider server 470 may be maintained by a payment provider,such as PayPal, Inc. of San Jose, Calif.

Client device 410, merchant server 440, and payment service providerserver 470 may each include one or more processors, memories, and otherappropriate components for executing instructions such as program codeand/or data stored on one or more computer readable mediums to implementthe various applications, data, and steps described herein. For example,such instructions may be stored in one or more computer readable mediumssuch as memories or data storage devices internal and/or external tovarious components of system 400, and/or accessible over network 460.

Network 460 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 460 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks.

Client device 410 may be implemented using any appropriate combinationof hardware and/or software configured for wired and/or wirelesscommunication over network 460. For example, in one embodiment, clientdevice 410 may be implemented as a personal computer of a user 405 incommunication with the Internet. In other embodiments, client device 410may be implemented as a wireless telephone, personal digital assistant(PDA), notebook computer, and/or other types of computing devices.

As shown, client device 410 may include one or more browser applications415 which may be used, for example, to provide a convenient interface topermit user 405 to browse information available over network 460. Forexample, in one embodiment, browser application 415 may be implementedas a web browser configured to view information available over theInternet.

Client device 410 may also include one or more toolbar applications 420which may be used, for example, to provide client-side processing forperforming desired tasks in response to operations selected by user 405.In one embodiment, toolbar application 420 may display a user interfacein connection with browser application 415.

Client device 410 may further include other applications 425 as may bedesired in particular embodiments to provide desired features to clientdevice 410. In particular, applications 425 may include a paymentapplication and button, such as described herein for same screen quickpayments through a payment provider. Applications 425 may also includesecurity applications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 460, or othertypes of applications. Email applications may also be included, whichallow user 405 to send and receive emails through network 460. Clientdevice 410 includes one or more user and/or device identifiers 430 whichmay be implemented, for example, as operating system registry entries,cookies associated with browser application 415, identifiers associatedwith hardware of client device 410, or other appropriate identifiers,such as a phone number. In one embodiment, user identifier 430 may beused by a payment service provider to associate user 405 with aparticular account maintained by the payment service provider as furtherdescribed herein.

Merchant server 440 may be maintained, for example, by an on-linemerchant or application developer offering various products and/orservices in exchange for payment to be received over network 460,including digital goods and applications. In this regard, merchantserver 440 includes a database 445 identifying available products and/orservices (e.g., collectively referred to as items) which may be madeavailable for viewing and purchase by user 405. Accordingly, merchantserver 440 also includes a marketplace application 450 which may beconfigured to provide information over network 460 to browser 415 ofclient device 410. For example, in one embodiment, user 405 may interactwith marketplace application 450 through browser applications overnetwork 460 in order to search and view various products or servicesidentified in database 445.

Merchant server 440 also includes a checkout application 455 which maybe configured to facilitate the purchase by user 405 of goods orservices identified by marketplace application 450. In this regard,checkout application 455 may be configured to accept payment informationfrom user 405 and/or from payment service provider server 470 overnetwork 460.

In one embodiment, merchant server 440 further includes a deliveryapplication 435 which may be configured to deliver a digital ordownloadable item to client device 410. For example, if user 405purchases a downloadable item from merchant, delivery application 435has the ability to transmit or download the item onto client device 410after payment is confirmed by payment service provider server 470.

Payment service provider server 470 may be maintained, for example, byan online payment service provider which may provide payment on behalfof user 405 to the operator of merchant server 440. In this regard,payment service provider server 470 includes one or more paymentapplications 475 which may be configured to interact with client device410 and/or merchant server 440 over network 460 to facilitate thepurchase of goods or services by user 405 of client device 410 from amerchant operating server 440. In one embodiment, payment serviceprovider server 470 may be maintained by PayPal, Inc.

Payment service provider server 470 also maintains a plurality of useraccounts 480, each of which may include account information 485associated with individual users. For example, in one embodiment,account information 485 may include private financial information ofusers of devices such as account numbers, passwords, credit cardinformation, bank information, or other financial information which maybe used to facilitate online transactions by user 405, as well as deviceinformation from a phone or PC that aids in determining whether apayment request is to be approved. Payment application 475 may beconfigured to interact with merchant server 440 on behalf of user 405during a transaction with checkout application 455 and deliveryapplication 435 to track and manage purchases made by users.

In particular, payment service provider server 470 also provides apayment button application 490 which may be configured load or installthe payment button onto client device 410. A payment button processingapplication 495 may be configured to receive payment request informationvia the payment button selected by users, process the payment request,and store/retrieve information as needed in a database 496. Paymentbutton application 490, processing application 495 and/or database 496may be part of payment application 475.

FIG. 5 is a block diagram of a computer system 500 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the user device may comprise a personalcomputing device (e.g., a personal computer, laptop, cell phone, PDA,etc.) capable of communicating with the network. The merchant and/orpayment provider may utilize a network computing device (e.g., a networkserver) capable of communicating with the network. It should beappreciated that each of the devices utilized by users, merchants, andpayment providers may be implemented as computer system 400 in a manneras follows.

In accordance with various embodiments of the present disclosure,computer system 500, such as a personal computer and/or a networkserver, includes a bus 502 or other communication mechanism forcommunicating information, which interconnects subsystems andcomponents, such as a processing component 504 (e.g., processor,micro-controller, digital signal processor (DSP), etc.), a system memorycomponent 506 (e.g., RAM), a static storage component 508 (e.g., ROM), adisk drive component 510 (e.g., magnetic or optical), a networkinterface component 512 (e.g., modem or Ethernet card), a displaycomponent 514 (e.g., CRT or LCD), an input component 516 (e.g.,keyboard, keypad, or virtual keyboard), and a cursor control component518 (e.g., mouse, pointer, or trackball). In one implementation, diskdrive component 510 may comprise a database having one or more diskdrive components.

In accordance with embodiments of the present disclosure, computersystem 500 performs specific operations by processor 504 executing oneor more sequences of instructions contained in system memory component506, such as described above with respect to the consumer and/or paymentprovider in FIGS. 1-3. Such instructions may be read into system memorycomponent 506 from another computer readable medium, such as staticstorage component 508 or disk drive component 510. In other embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions to implement the present disclosure.

Logic may be encoded in a computer readable medium, which may refer toany medium that participates in providing instructions to processor 504for execution. Such a medium may take many forms, including but notlimited to, non-volatile media, volatile media, and transmission media.In various implementations, non-volatile media includes optical ormagnetic disks, such as disk drive component 510, volatile mediaincludes dynamic memory, such as system memory component 506, andtransmission media includes coaxial cables, copper wire, and fiberoptics, including wires that comprise bus 502. In one example,transmission media may take the form of acoustic or light waves, such asthose generated during radio wave and infrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, carrier wave, or anyother medium from which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled by acommunication link 520 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Computer system 500 may transmit and receive messages, data, informationand instructions, including one or more programs (i.e., applicationcode) through communication link 520 and a communication interface 512.Network interface component 512 may include an antenna, either separateor integrated, to enable transmission and reception via communicationlink 520. Received program code may be executed by processor 504 asreceived and/or stored in disk drive component 510 or some othernon-volatile storage component for execution.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. For example, thepayment button and processing has been described with respect to apayment provider, but some or all of the features and steps may beassociated with a mobile platform and/or a merchant. Having thusdescribed embodiments of the present disclosure, persons of ordinaryskill in the art will recognize that changes may be made in form anddetail without departing from the scope of the present disclosure. Thus,the present disclosure is limited only by the claims.

1. A method of performing on-line payments, comprising: receiving apayment request from a user for an item to be purchased, wherein thepayment request is received from a payment button on an item screen fromwhich the item was selected; receiving information about the paymentrequest; processing the payment request based on the information; andnotifying the user, wherein the payment button remains on the itemscreen during the processing.
 2. The method of claim 1, wherein thepayment button changes during different portions of a payment process.3. The method of claim 1, wherein the item screen is on a mobile phone.4. The method of claim 1, wherein the user enters only an identifierwhen paying for the item.
 5. The method of claim 4, wherein theidentifier is a password or PIN.
 6. The method of claim 1, wherein thepayment button allows the user to enter information on the paymentbutton.
 7. The method of claim 1, wherein the payment request isreceived from the user via a mobile device.
 8. The method of claim 1,wherein the information comprises a purchase amount, merchantinformation, a device identifier, and/or a user identifier.
 9. Themethod of claim 1, wherein the notifying is on the payment button. 10.The method of claim 1, wherein the payment button has conditions for usepredetermined by the user.
 11. The method of claim 1, wherein the itemscreen is a merchant page.
 12. The method of claim 1, wherein the itemscreen is an applications page.
 13. The method of claim 1, wherein theitem is a downloadable digital good.
 14. A mobile communication devicefor financial transaction, comprising: an antenna configured tocommunicate with a payment provider; a processor configured to display apayment button generated from the payment provider; a memory to storeinformation about the financial transaction, wherein the financialtransaction comprises a purchase and a payment of an item; and a displayto display the payment button, wherein the payment button changes andremains on a window where the item was purchased during a paymentprocess.
 15. The device of claim 14, wherein the payment processrequires the user to enter only an identifier when paying for the item.16. The device of claim 14, wherein the payment button allows the userto enter information on the payment button.
 17. The method of claim 14,wherein the payment button notifies the user of the status of thepayment process.
 18. A machine-readable medium comprising a plurality ofmachine-readable instructions which when executed by one or moreprocessors of a server are adapted to cause the server to perform amethod comprising: receiving a payment request from a user for an itemto be purchased, wherein the payment request is received from a paymentbutton on an item screen from which the item was selected; receivinginformation about the payment request; processing the payment requestbased on the information; and notifying the user, wherein the paymentbutton remains on the item screen during the processing.
 19. Themachine-readable medium of claim 18, wherein the payment button changesduring different portions of a payment process.
 20. The machine-readablemedium of claim 18, wherein the payment button allows the user to enterinformation on the payment button.
 21. The machine-readable medium ofclaim 18, wherein the payment button notifies the user of a status ofthe processing.
 22. An on-line payment system comprising: means forreceiving a payment request from a user for an item to be purchased,wherein the payment request is received from a payment button on an itemscreen from which the item was selected; means for receiving informationabout the payment request; means for processing the payment requestbased on the information; and means for notifying the user, wherein thepayment button remains on the item screen during the processing.
 23. Theon-line payment system of claim 22, wherein the user enters only anidentifier when paying for the item.
 24. The on-line payment system ofclaim 22, wherein the payment button allows the user to enterinformation on the payment button.
 25. The on-line payment system ofclaim 22, wherein the payment button notifies the user of a status ofthe processing.